Esri Enterprise Geodatabase

Read and Write Support

Data Store Type	As standard		Using FME Desktop
Data Store Type	Write	Read	Read	Write
Esri Enterprise Geodatabase

Commit Support

Data Store Type	Task Supported
Esri Enterprise Geodatabase

Data Store Type

Task Supported

Commit

Copy-to

Esri Enterprise Geodatabase

Key Information

This format is only available on Windows.
Requires FME Desktop (64-bit) Esri Edition, and ArcGIS Desktop, ArcGIS Desktop Background Processing (64-bit) and Database client (64-bit).

Note: In order to use the Esri Enterprise Geodatabase datastore format, ArcMap (64-bit) and FME Desktop Esri Edition must be installed and a licence for each available on the machine(s) running 1Integrate (and all engines). For full details, see the FME knowledge centre.

Input and Output Connection

Input connection

Parameter	Description
Source Database	The name of the database.
Coordinate Reference System	Coordinate Reference System parameters are required in a session that will write data to Oracle. This parameter can be used to specify a Coordinate Reference System (CRS) code of the input data, if it cannot be deduced automatically. This will not re-project the data, but allows its current CRS to be defined (e.g to enable multiple data stores to open where one does not have a CRS defined). See Coordinate Reference System for more information on when this is required.
Import FME Log File	Download the FME log file created during import (to help identify any errors).
Allow invalid geometries	Allows features with invalid geometries (e.g. duplicate vertices, self-intersections) to be imported. This is necessary if they need to be imported in order to be validated or corrected. If not ticked then features with invalid geometries are not imported and are logged as feature errors in the open data task.
Enable full 3D Geometries (BETA)	Select to enable full 3D geometries. Note: This parameter will only appear with an additional license enabling 3D support within 1Integrate. For more information on full 3D in 1Integrate, please see 3D Support.
Fix ring direction and inclusion errors	Polygon rings are assumed to be encoded using the right-hand rule, i.e. outer rings are anti-clockwise and inner rings are clockwise. If the service does not guarantee that encoding, then set this flag to have polygon rings automatically oriented on import to avoid later problems when processing the data. Note: This requires a small amount of additional processing so only set if the ring direction is not guaranteed.
Reverse Coordinate axis order (y, x)	Reverse the x and y co-ordinate values. Select this if the coordinates are in (y,x) order and are not being read or written in the correct order.
Connection File	Select a connection file (.sde) to be used to connect to the Esri Enterprise Geodatabase.
Dataset	The name of the dataset from which features will be retrieved.
Server	The name of the Geodatabase server used to read data from the dataset.
Instance Name	The name of the Enterprise Geodatabase instance. Note: The typical value for systems with a single ArcSDE instance is esri_sde8.
User ID	User ID of the Enterprise Geodatabase user.
Password	Password for the User ID.
Version	If you're using a versioned dataset and you want to connect to a specific version, then you need to enter the version name and specify VERSIONING as the Transaction Type. If using a non-versioned database or if connecting to the DEFAULT version, then leave this blank.
Transaction Type	Specify the type of transaction to use when accessing and updating the data. The types are VERSIONING, EDIT_SESSION, TRANSACTIONS or NONE. If not specified then the default is TRANSACTIONS. For further information about transaction types refer to FME documentation. If using a non-versioned database, leave this blank.
Retrieve All Schemas	Must be checked to allow import schema refresh.
Remove Table Qualifier	Specifies whether to keep or remove the table name prefix. For example, if set, "ROAD_NETWORK.NONCONFORMANCE" will become "NONCONFORMANCE".
Clip to envelope	If selected, causes features that overlap the bounding box (defined in the Search Envelope parameter) to be clipped and the outer part discarded. Note: This should only be used when a session is loading a subset of the data by defining an extent as a bounding box or polygon. If set, it causes features that overlap the extent to be clipped and the outer part discarded. If not selected then the whole geometry of features that intersect the extent will be loaded including the parts of their geometry that are outside the extent.
For X, Y, Z, M data:	If you have data that is recorded as X,Y,Z,M, you must opt to ignore either Z or M values by choosing to use X, Y and M or X, Y and Z only. Note: If the default is left on and X,Y,Z,M is uploaded then an exception will be thrown as 1Integrate only supports X,Y,M or X,Y,Z.
For X, Y, Z, M data: Use zero rather than NULL or NaN when writing ignored ordinate	Select to write ignored values as zero in place of null.

Output connection

Parameter	Description
Destination Database	The name of the database.
Coordinate Reference System	Required if the data store will be used in a session that will write data to Oracle. This can be used to specify the CRS of the output data if it cannot be deduced from the input data. This will not re-project the data, but allows it’s current CRS to be defined. See Coordinate Reference System for more information on when this is required.
Export FME Log File	Download the FME log file created during export (to help identify any errors).
Reverse coordinate axis order (y, x)	Reverse the x and y co-ordinate values.
Connection File	Select a connection file (.sde) to be used to connect to the Esri Enterprise Geodatabase.
Dataset	The name of the dataset from which features will be retrieved.
Server	The name of the Geodatabase server used to read data from the dataset.
Instance Name	The name of the Enterprise Geodatabase instance. Note: The typical value for systems with a single ArcSDE instance is esri_sde8.
User ID	User ID of the Enterprise Geodatabase user.
Password	Password for the User ID.
Persistent Connection	Select to keep a connection open and save the processing time required to make and break a database connection.
Commit Transactions After Write	Specifies whether to commit transactions at the end of each write operation. Note: Only valid when the versioning type is set to "transactions".